ci: run check-file-headers in GitHub Actions #1144
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This has probably been discussed before, but I'm wondering what the benefit is of running the same check in CircleCI and Github Actions. It's not the case that the check of file headers would fail in one but not the other, right? Could we forego CircleCI and just use GitHub Actions? Or in the reverse direction, could we remove standard-suite.yml in favor of CircleCI? I'm just curious about whether both sets of checks are needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the only step present in
.circleci/config.ymlthat is currently missing from.github/workflows/standard-suite.yml.